feat(brand): draw the small-size optical cut at chrome sizes - #2473

Summary

• The follow-up recorded in feat(design-system): give the brand a written identity and a per-ground mark #2462 and deliberately left undone there, now that the artwork decision has been made. The app rendered the mark's display geometry at every size, including the 28–32px chrome where the brand's own construction calls for a different cut.
• Why this is the real fix, and the previous one was compensation. The mark is a construction, not a bitmap, so it does not simply get smaller. Two pieces of its negative space close up first — the 4.2-unit cut between the strokes and the 7.26-unit crescent around the point — and when the crescent closes, the dot fuses into the S. That fuses the top of the mark into one solid blob above a lower stroke that is already the thinner read. That is the top-heavy look, which feat(design-system): give the brand a written identity and a per-ground mark #2462 offset with the deeper --brand-mark-emphasis ink. The ink stays; the cause is now addressed rather than offset.
• The remedy was already specified and already shipped — nothing used it. docs/brand/psychsift-logo.md §"Small sizes" calls for it, and brand-mark.ts already exports BRAND_STROKE_PATH_SMALL (cut opened to 7.2 units) and BRAND_POINT_SMALL (point slid 10 units out of its cradle, crescent opened from 7.26 to 11.55). Only the favicon and the raster icon routes consumed them.
• Sub-32px production sites now draw the chrome cut: the collapsed sidebar rail (28px), the phone drawer header (28/32px), the account-setup workspace mark (32px), and the ward sidebar glyph (32px). Everything at 36px and above keeps the display cut. Design-scratch mockups are untouched.
• The three pieces are selected together through one brandMarkOptics() call, so a caller cannot half-apply the variant — the brand doc is explicit that mixing one variant's point with the other's placement puts the glyph off-centre in its box.

The one thing that did not exist, and how it was derived rather than drawn

The bare (untiled) glyph had no small-size placement. brand-mark.ts says in terms not to redraw the construction by hand, and this does not.

The doc fixes both ink boxes — display spans 0–55.33, chrome 0–65.33, both 0–100.38 tall — and every committed placement centres that box in the 512 viewBox. That rule was checked against all three existing transforms before anything was written: each lands its centre on 256.000 within 0.003, the rounding of a two-decimal box figure.

Two consequences then follow arithmetically rather than by eye:

• The point keeps its cy and r, so the vertical extent is identical and the scale is unchanged at 5.1006 — 100.3813 × 5.1006 = 512.0, which is the bare variant's whole purpose.
• The point moves exactly 10 units and is the box's right edge, so the box widens by 10 and its centre by 5: 114.8907 − 5 × 5.1006 = 89.3877.

The same arithmetic reproduces the committed tiled pair (143.1125 − 5 × 4.0804 = 122.7103, as shipped). That is the check that this is the rule actually in use, not merely one that fits the numbers.

Threshold is 32px, from the doc's own "at 32 px and below two things close up". Below ~20px the crescent is under two pixels whatever is done; that is the size, not the placement, and no variant rescues it.

Verification

• tests/brand-mark-optics.test.ts — 14 passed. Every new rule mutation-tested with the failure predicted before running, then compared against observed: dropping optical="chrome" from a 28px site, adding it to a 40px one, shifting the new transform 5px off centre, and pairing the chrome placement with the display point each failed exactly the intended assertion (1 failed, 2 failed, 3 failed, 2 failed respectively). All four restored byte-identical.
• Writing that test surfaced a defect in the test itself, fixed before it could mislead. ward-management-navigation.tsx imports two CSS modules that both define .brandGlyph, at 2.5rem and 2rem; an identifier-blind resolver merged them and reported real call sites as spanning the threshold — a helper bug that reads exactly like a source bug. It now resolves the specific import identifier. The same run caught sidebar-live-mockup.tsx, design scratch named with the singular -mockup, which the usual mockups filter misses.
• npm run brand:check — ✓ brand: src/app/icon.svg matches the brand-mark source. This change adds exports and alters no existing value, so the generated assets are untouched.
• npm run check:design-system-contract — passed, every ratchet at or under baseline (sub-floor interactive min-heights 2, matching). Adoption 55 components / 84 roots; design-sync contract 55 components / 7 guidelines.
• npm run build on a cleared .next — succeeded, Client bundle secret surface check passed.
• npm run test — 11744 passed | 1 skipped across 931 files. Three pre-existing failures in clinical-hazard-controls, privacy-readiness-contract and rag-plan-package-parity, reproduced identically on a clean origin/main checkout in this same container (3 failed | 22 passed). None touches brand geometry, and CI's Unit coverage passed all three on feat(design-system): give the brand a written identity and a per-ground mark #2462, so they are container-local rather than repository defects.
• npm run lint clean at --max-warnings 0; npm run typecheck exit 0, unscoped; npm run format whole-tree, committed with the work.

UI verification not run: npm run verify:ui needs a dev server and a Chromium pass I did not confirm ready in this container; the Chromium journeys in CI are the gate of record. Worth stating plainly — this change is visual, and the evidence above is arithmetic and structural, not a rendered comparison. The geometry is the brand's own committed artwork and the placement is verified against the rule the existing transforms already follow, but nobody has yet looked at the new cut on a phone. That is the one check this PR cannot supply.

Risk and rollout

• Risk: Low, and visually narrow. No data, no schema, no retrieval, no auth, no layout. Only the d attribute, one circle's cx, and a transform change, on marks rendered at 28–32px. The outer silhouette is identical between the two cuts by construction — only the facing edges and the point move — so this cannot alter the mark's footprint or the space it occupies.
• Rollback: single-commit revert. The optical prop defaults to display, so reverting the call sites alone restores the previous appearance without touching the geometry exports.
• Provider or production effects: None. Every gate above is local and offline; no OpenAI, Supabase, Railway or hosted-CI call was made.
• RAG impact: no retrieval behaviour change — this diff touches no file under src/lib/rag/** and none of the protected ranking surfaces (clinical-search, retrieval-selection, released-search-order, ranking-config, answer-ranking, answer-verification), adds no comparator key, and leaves the golden fixture and eval harness untouched. Verified by listing the diff's seven paths against that set.

Clinical Governance Preflight

• Source-backed claims still require linked source verification before clinical use
• No patient-identifiable document workflow was introduced or expanded without explicit governance approval
• Supabase target remains Clinical KB Database (sjrfecxgysukkwxsowpy)
• Service-role keys and private document access remain server-only
• Demo/synthetic content remains clearly separated from real clinical sources
• Source metadata, review status, and outdated/unknown-source behavior remain conservative
• Deployment classification/TGA SaMD impact was checked when clinical decision-support behavior changed

Notes against those items, in full rather than as ticks alone.

This change introduces no retrieval path, no source-backed claim, no clinical content, no copy and no new data. It changes which of two committed vector constructions is drawn for the brand mark at small sizes. No Supabase target, migration, credential or document-access path is touched, and nothing added here runs server-side.

There is no clinical surface in this diff. The nearest thing is the account-setup workspace mark and the ward sidebar glyph, and in both cases the change is the logo's own geometry — no clinical value, status, badge, threshold or absence wording is involved, and nothing about what any page discloses or how it degrades has moved.

Failure behaviour is unchanged. Nothing here sits on a degradation path: brandMarkOptics() is a pure selector over build-time constants with a display default, so an unrecognised or absent variant draws the primary construction rather than nothing. The mark renders identically whether or not any runtime data resolves.

Notes

Still open, and still the owner's call: the phone chrome band on the privacy route paints --surface-glass at 95%, which reads whiter than the tinted page beneath it and leaves a seam the mark appears to float on. It was raised in #2462 and remains unaddressed here for the same reason — moving a phone chrome ground is docs/search-chrome-behaviour.md territory and wants verify:phone-chrome evidence of its own. It is a separate change, not a line to slip into this one.

Also unchanged and not fixable from the repository: Cursor Bugbot has now failed to run on two consecutive PRs against a Cursor usage/spend limit, so it has reviewed neither. That is an account setting, not a code problem.

Generated by Claude Code